Within the team, you need to come to a common understanding of the boundaries of the organization that you are
describing and decide which processes you will need to describe in more detail.
The purpose of this activity is to:
-
Decide on terminology.
-
Identify business goals that support the business strategy.
-
Outline the business use-case model.
-
Prioritize which business use cases to describe in detail.
It starts with identifying the current Business Goals. This is done in parallel to refining the existing Business Actors. Business Use Cases should reflect the target organization. Depending
on the scope of the business-modeling effort defined in the Business Vision, the existing business actors and business use cases
might be used as a starting point and refined or completely rethought.
Business use cases are detailed just enough to understand their impact and prioritize them. In practice, a rough
outline of each business use case should be adequate. Where quantitative or qualitative requirements (such as minimum
throughput or adherence to standards) that govern the behavior of the business use cases are uncovered, they must be
documented in the Supplementary Business Specifications.
Commonly used terms and definitions must be captured in the Business Glossary. Any business rules discovered during this process
must be documented in the Business Rules.
Based on the business-modeling objectives as defined in the Business Vision, the business use cases are prioritized, and the
Business Process View of the Business Architecture Document is updated with the (adjusted)
architecturally significant business use cases.
|
This content developed or partially developed by Empulsys BV.
|
|
|